chore(deps): group Dependabot updates into a single PR per ecosystem - #32
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
codenamev
approved these changes
Aug 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This repo is the source of the #14–#23 PR spam: Dependabot was weekly but fully ungrouped, so every dependency got its own PR. Adds a
groupsblock matching*to every ecosystem in.github/dependabot.yml, so each weekly run produces one consolidated PR per ecosystem+directory.Note: a Dependabot group is scoped to one ecosystem + directory, so bundler and github-actions still open separate PRs — that's the floor, not a config miss. Grouping is also not retroactive; the ten already-open individual PRs stay open and need separate triage.
🤖 Generated with Claude Code